|
|
|
|
|
Hi Mr Kang, Since we are still waiting for reference driver source from Synaptics and ESMT, the schedule may depends on when we get the reference source drivers. If we can get the reference driver by 8/12, the expected schedule to provide this app is 9/14 (a week later after drivers are integrated). |
|
|
Hi Mr. River Weng, I think it make some delay on our mechanical schedule. SKT will decide FF MIC location based on test using your test application. So could you provide test app by the end of Aug ? |
|
|
Hi Mr. Yoon, The test app will work only after ADV/AMP drivers are ready and audio routing to framework is ready. From current schedule, it will be tough to provide the app by end of Aug. But we will try our best to first focus on porting drivers for MIC ADC and AMP at board bring-up stage and try to shorten the porting time for these two drivers. |
|
|
Hi River, As comment in attached document, to do test echo environment, App should be possible music play and mic record at the same time, I just want you to know, because SKT engineer advises it to us again. Thanks. |
|
|
Hi Wooshin, We understand your requirement, We are developing the app to play file to 2 AMP speakers and record 4 channels audio data from 4 far field microphones at the same time. |
|
|
Hi Wooshin, I upload the image and app to https://drive.google.com/file/d/1Ose0S7dA9mNrFhktL_BYNUotXMOWapeH/view?usp=sharing unzip the file, there is an image and an app: 1.eMMCimg folder: This is a image. Please update it with SPI card. 2.SWANTool.pak: Please use adb install to install this app. For example the box has ip address 192.168.0.10: adb connect 192.168.0.10:5815 adb install SwanTool.apk How to run App: 1.Settins->Apps->See all apps->Show system apps->SWANTool->open Select "Allow" twice. 2.Adjust Volume to Maximum. 3.Mute TV HDMI audio by TV remote. (Because we will output audio to speakers and hdmi at the same time). 3.Put a play.wav file in a usb storage with FAT32 file system and plug the usb storage to our main board. 4.When recording file, please wait for the "File Sync OK". Then the rec.wav will copy to usb storage. PS; please remember the usb storage should be FAT32 format. |
|
|
Dear River, Thanks for your work but, SKB request us like below. In case of audio playback function, they want file list and can select to play in that file list. Files in list should be able to play in app. (You can use file extend to sort file in list) Please modify app include file list. And SKB want below pem info for 4 mic + 2 ref. (device number, card number, samplerate, channel count, bitrate, period size, period count etc) Thanks KANG, |
|
|
Hi Wooshin, For the file list to play, could we list only .wav files in root directory of usb? The pcm info is: tinycap temp.wav -D 0 -d 1 -c 2 -r 48000 -b 32 -p 256 -n 8 Please note, the temp.wav is only 2 channel wav file. We change the header of temp.wav from 2 channel 32bits to 4 channel 16bits to seperate the I2S TDM data and save it to rec.wav in this app. The rec.wav file is already a 4 channels wav file (each sample is 16bits per channel). |
|
|
Dear River, I think it is better folder "/mnt/media_rw/sdcard3/music" and add wav and mp3. thanks KANG, |
|
|
Dear River, Please inform us about "PCM info" used when you make temp.wav file, Thanks KANG |
|
|
Hi Wooshin, The pcm info is already mentioned in 0000871:0004276. I post it again. The pcm info is: tinycap temp.wav -D 0 -d 1 -c 2 -r 48000 -b 32 -p 256 -n 8 Please note, the temp.wav is only 2 channel wav file. We change the header of temp.wav from 2 channel 32bits to 4 channel 16bits to seperate the I2S TDM data and save it to rec.wav in this app. The rec.wav file is already a 4 channels wav file (each sample is 16bits per channel). |
|
|
Hi Wooshin, I upload the new image and app to https://drive.google.com/file/d/1gc_l7XRpH17KxUai3A4WFsMrglTuw_0n/view?usp=sharing Please download and check it. Thanks. |
|
|
Dear River, We need 4 channel 16 bits temp.wav file and 2 channel 32 bit temp.wav file. Please save this files to USB. And, we are doing AMP tune with dreamus, and they will give some best velue for AMP. If i get, I will give you and please build gain with upper requirement. Thanks. KANG |
|
|
Hi Wooshin, We will wait for dreamus best value from you. And then give you new app to add 2 channels 32 bit wav file and keep recv.wav file for 4 channels 16 bits. |
|
|
Hi River, To make clear, list up need file. < 4 channel mic > 1. 4 channel 32bit format file. ( This is origin file from tinycap ) 2. 4 channel 16bit format file. ( This file is made by FXN, for android). <Ref 2 channel mic > 1. 2 channel 32bit format file. ( This is origin file from tinycap ) 2. 2 channel 16bit format file. ( This file is made by FXN, for android). Is it possible to make ? And, if there is wrong information in my requirement, please inform me. Thanks. KANG, |
|
|
Hi Wooshin, < 4 channel mic > 1. 4 channel 32bit format file. ( This is origin file from tinycap ) --> We do no have this file. It is 2 channel 32bits format file from tinycap. 2. 4 channel 16bit format file. ( This file is made by FXN, for android). --> We have this file. It is rec.wav. We separate the file from tinycap to 4 channel 16 bits. About the <Ref 2 channel mic >, do you mean the Speaker loopback reference audios for audio processing? If yes, we do not implement in app. It will be 2 channels 32 bits format and we will not separate it because it is a standard I2S data. If no, there are 4 far field microphones, I do not know which 2 microphones you want? |
|
|
Hi Wooshin, < 4 channel mic > 1. 4 channel 32bit format file. ( This is origin file from tinycap ) --> We do no have this file. It is 2 channel 32bits format file from tinycap. [KANG] ==========> (OK) 2. 4 channel 16bit format file. ( This file is made by FXN, for android). --> We have this file. It is rec.wav. We separate the file from tinycap to 4 channel 16 bits. [KANG] ==========>(OK) About the <Ref 2 channel mic >, do you mean the Speaker loopback reference audios for audio processing? [KANG] Yes, it is speaker loopback reference. Let's go like your note "We will wait for dreamus best value from you. And then give you new app to add 2 channels 32 bit wav file and keep recv.wav file for 4 channels 16 bits." Thanks |
|
|
Dear River, I have gotten tune value from dreamus and attache that. Please find it and release nwe image and app. Thank. KANG, |
|
|
Hi Wooshin, I upload the new image and app to https://drive.google.com/file/d/1qzSDqRmjTPM4tj1pEbjoAXrqwl9aS-QZ/view?usp=sharing Please download and check it. We also changed the file name. The 2 channels 32 bit file name is rec_2C32B.wav and 4 channels 16 bit file name is rec_4C16B.wav. Thanks. |
|
|
Hi Wooshin, I upload the new image and app to https://drive.google.com/file/d/1HYprWjIhGFCzeG0KYKbnST96_rfdovNy/view?usp=sharing Please download and check it. The rec.wav is 4 channels 16 bits of Far Field MIC. The ref.wav is 2 channels 32 bits of reference loopback audio. When you eject the usb, please use the "Settings->Device Preferences->Storage->Select your usb device->Eject". It will make sure the rec.wav and ref.wav will be flush to usb. Please note that the ref.wav can not be played by our app (32bits wav can not be played). You can use mediaplayer of windows to play it. |
|
|
Dear River, I have done test is. I looks it is working correctly. If i get feedback from SKT, let you Know. Thanks. KANG |
|
|
Dear River, I got a feedback from SKT, they told there is data loss in rec.wav. Is it related with data drop of aux input ? I guess it is same issue. KANG |
|
|
Hi Wooshin, Yes, it seems all the I2S input (Far Field MIC, loopback, AUX/Karaoke MIC) will sometimes have audio data loss. We reported it to Synaptics and Kail is looking on this issue. If possible, please also help to push Synaptics to solve it. |
|
|
Dear River, At this moment, I am pushing kail. Thanks. |
|
|
Hi Wooshin, I remembered you ask me about the pcm info (device number, card number, samplerate, channel count, bitrate, period size, period count etc). As we know, the period count is related to dma buffer size. We wants to know the pcm info about AI2 for reference. Could you help to check with SKB that what pcm info are used for AI2? |
|
|
Dear River, Actually, mic hal implementation was role of manufacturer because NUGU is not made by SK in AI2. So, i got a information from my friend of AI2 manufacturer. Please check below, it is not differ with yours struct pcm_config alsa_config; alsa_config.channels = 2; alsa_config.rate = SYNA_ALSA_PARAM_RATE; alsa_config.format = PCM_FORMAT_S32_LE; alsa_config.period_size = SYNA_ALSA_PARAM_PERIOD; alsa_config.period_count = SYNA_ALSA_PARAM_N; alsa_config.start_threshold = 0; alsa_config.stop_threshold = 0; alsa_config.silence_threshold = 0; #define SYNA_ALSA_PARAM_PERIOD 256 #define SYNA_ALSA_PARAM_N 8 #define SYNA_ALSA_PARAM_RATE 48000 |
|
|
Hi Wooshin, We built an eMMCimg and an apk with Synaptics I2S audio drop patch. https://drive.google.com/file/d/1IE1guIkGOPJVdBLsJw6EuEFuLtAmI5CN/view?usp=sharing If you want to try, you can use it. The reference audio parameters of tinycap: tinycap /data/reference.wav -D 0 -d 0 -c 2 -r 48000 -b 32 -p 384 -n 16 The far field mic parameters of tinycap: tinycap /data/ffv.wav -D 0 -d 1 -c 2 -r 48000 -b 32 -p 384 -n 16 |
|
|
Hi Wooshin, We use latest Synaptics I2S audio drop patch(release on 10/07) to build am eMMCimg and app. I think the patch can fix the I2S drop issue. Please give use the image for mic tuning. https://drive.google.com/file/d/1CJzIhUSBMWeFeC2IXdQRvVBS_rttCwdd/view?usp=sharing For your reference, the parameters to capture the audios: tinycap /data/loopback.wav -D 0 -d 0 -c 2 -r 48000 -b 32 -p 256 -n 16 tinycap /data/ffv.wav -D 0 -d 1 -c 2 -r 48000 -b 32 -p256 -n 16 |
|
|
Dear River, Please make new image on following environment. 1. We need to make new image on applied M1 SDK + "0001-asoc-syna-enable-disable-i2s-port-by-channel.patch". 2. When we check "rec.wav", mic position is not "1, 2, 3, 4" from left. Please change it to "1,2,3,4" from left. 3. We need only "rec.wav", we don't need ref.wav in this version. Thanks. |
|
|
Hi Wooshin, For 2, because all the boxes with housing are taken by HW engineer to other labs for testing. Could you take a picture of the pcb to show which MIC is the 1,2,3 and 4? For 3, we will still keep the ref.wav in case you will need it. Because even with latest patch, rec.wav can only get 4 channel FFV audio data (it will not include reference audio.) From your email "After patching it, you can get 6 channel data (ffv + loopback) from pcm_open with channel 1." , this is not right. You should not be able to get 6 channels audio data from one pcm_open(). |
|
|
Hi River, You can see the silk print on the MIC PCB. MIC 1/2/3/4 order is U6_5/MIC4, U6_4/MIC3 / U6_3/MIC2 / U6_2/MIC1. If you have any question, please let us know. |
|
|
This comment is for writing history. 2. I have sent image by wechat. 3. About patch, you can communication directly with synaptics guy on link. https://synaextjira.atlassian.net/jira/software/c/projects/SKBSBALT/issues/SKBSBALT-40 |
|
|
Dear River, About 4 ch mic order, if you have any concern, Please inform us. Thanks. |
|
|
Hi Wooshin, I post a picture below with the real sub-PCB label of U6_5/MIC4, U6_4/MIC3 / U6_3/MIC2 / U6_2/MIC1. If from left, the order should be U6_2/MIC1 , U6_3/MIC2 , U6_4/MIC3 , U6_5/MIC4. It is different from your comment above. Could you check it again and confirm which order you want? |
|
|
Dear River, Yes, it is right. Thanks. |
|
|
Hi Wooshin. So, is my order is right or your order is right? |
|
|
Hi Wooshin, As we discussed today, the reference audio position and FFV MIC positions of rec.wav will be as the attached file. |
|
|
Hi Wooshin, We built the app and image which include the I2S 8 channel (each 16bits). The record file will be rec.wav in usb root folder. (it will not generate ref.wav). The each channel order is list in previous comment "8ch_16bits_audio_order.png". Please find the image and app in the following link: https://drive.google.com/file/d/1sntaAWH9ukTlkJGu566It954Sii9YW_e/view?usp=sharing Please note: the usb storage can only be plugged to the USB3.0 port. (USB2.0 port is now for usb adb on our debug image only). You can check the following picture about the USB3.0 port position usb3_port_postion.jpg (120,508 bytes) |
|
|
Hi Wooshin, The 10/21 app and image use the following tinycap parameters: tinycap /data/test.wav -D 0 -d 0 -c 4 -r 48000 -b 32 -p 256 -n 8 Note: we modify the test.wav header to 8 ch 16bits and save it to rec.wav in usb. |
|
|
Dear River, I need image which is included all patch of synaptics for audio data drop. Please release image. thanks. |
|
|
Hi Wooshin, After 10/21 image we released to you, we did not get any new patch to fix audio drop from Synaptics. (Jira 67 patch is not working) As I know, Synaptics only advise to use command to disable BT to avoid audio drop. service call bluetooth_manager 8 |
|
|
Hi River, Thanks for information. |
|
|
Hi River, Please make new image using below parameters: It is confirmed by SKT. tinycap /data/test.wav -D 0 -d 0 -c 2 -r 48000 -b 32 -p 384 -n 32 -T 30 Thanks. |
|
|
Hi Jerry, Per talked, please build image with app by using new parameters mentioned by Wooshin. |
|
|
Hi Wooshin, The command you provided will fail to capture audio data(all audio data are zero) tinycap /data/test.wav -D 0 -d 0 -c 2 -r 48000 -b 32 -p 384 -n 32 -T 30 Does the -c should be 4 or 2? please confirm it, |
|
|
Hi Wooshin, Sorry, it is no all zero, it only get the reference data when -c=2. |
|
|
Hi River, I am sorry wrong information. Below is right. tinycap /data/test.wav -D 0 -d 0 -c 4 -r 48000 -b 32 -p 384 -n 32 Thanks. |
|
|
Hi Wooshin, We built an eMMCimg and an apk. Please download from the following link: https://drive.google.com/file/d/1JFQV4AxbcfHa9OtTDJ56A__cfWjT9_7i/view?usp=sharing Jerry |
- yk.jung ( (ALTech) Younkwang Jung ) developer
